All of a sudden my Windows 7 x64 computer is unable to connect to random Windows 2008 R2 servers via Remote Desktop.

I can connect to the same servers from other Windows 7 machines.

The only fix I've come across so far is this, except that key doesn't exist on either my machine or on the server(s):

To resolve this issue, follow these steps:

1. Start Registry Editor.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters
3. Under this registry subkey, delete the following values:
   • Certificate
   • X509 Certificate
   • X509 Certificate ID
4. Quit Registry Editor, and then restart the server.

Does anyone have any suggestions please as I'm at a total loss what is happening here.

Thanks.

Hi,

You can try to configure the target server NIC properties to see whether solve this issue.

Local Area Connection -> Properties -> Configure -> Advanced -> IPv4 Large Send Offload =Disabled.

If it doesn't solve this issue, you can open the regedit.exe on target server, and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters

After exporting this for safekeeping, then you can delete the Certificate keys. Reboot the target server to see whether the same issue still exists.

Clarence

I know this is ancient, but I thought that I'd add what I found to be my solution after having the exact same issues as yourself, trying the suggested fixes without luck and just about pulling my hair out too:

My Fix:  Simply uninstall the Link-Layer Topology (Mapper I/O Driver and Responder) protocols, as well as the QoS Packet Scheduler service (you can add them back again afterwards) in the Local Area Connection of the client machine (not the server/target).  You must uninstall, not simply remove the checkmark next to the protocol or service.

This did the trick for me.

• Proposed as answer by AirborneAgain Friday, May 31, 2013 8:58 PM

Ancient or not, it helped me today.  I am connecting over a VPN, and I suddenly started getting this message when connecting to 5 different servers.  I knew it was on my end, so all of these suggestions for server changes weren't helping.  This took care of it, though.  Thanks, Garth.

thanks ! it worked like a charm ! i searched for dam long before seeing your reply

I uninstalled the Sonicwall Global VPN client and the problem went away.  In fact the VNC issues cleared up as well.  Haven't heard back from Sonicwall on the issue.

• Proposed as answer by Weeboo_TN Tuesday, November 04, 2014 4:17 PM

I uninstalled the Sonicwall Global VPN client and the problem went away.  In fact the VNC issues cleared up as well.  Haven't heard back from Sonicwall on the issue.

This resolved my problem. Thanks for the suggestion.

I uninstalled the Sonicwall Global VPN client and the problem went away.  In fact the VNC issues cleared up as well.  Haven't heard back from Sonicwall on the issue.

This fixed my issue, I'll have to find a work around to remote to my Sonic Wall network... Thank you Chris Kless

• Edited by Puente23 Sunday, October 06, 2013 4:37 PM

I uninstalled the Sonicwall Global VPN client and still had the issue.

Finally, removing Citrix DNE Lightweight Filter service from my network adapter solved the problem for me.

John

• Proposed as answer by Simon Carroll Thursday, October 31, 2013 11:25 AM

I uninstalled the Sonicwall Global VPN client and still had the issue.

Finally, removing Citrix DNE Lightweight Filter service from my network adapter solved the problem for me.

John

I'll second this, I connect to a couple of dozen different clients' servers using at least 10 different pieces of software; and I ripped out just about everything suggested here.  Only after uninstalling the Citrix DNE LightWeight Filter service from the network adaptor (and restarting) did the error go away.
I'm not putting back the other stuff (SonicWall client, Link-Layer Topology (Mapper I/O Driver and Responder) and QoS Packet Scheduler service) until this job is finished tomorrow, but I'll test as I add things back in and report back here.  

Thanks!  This worked for me too.  Server 2003, Windows 7 x64.

Simply running the Sonicwall client without actually connecting to any vpn actually resolved the issue for me.

• Proposed as answer by KBert99 Monday, May 12, 2014 3:18 PM

Yes... it wasn't the sonicwall client for me... it was the citrix DNE filter? Removing that allowed my sonicwall vpn to work again.

I uninstalled the Sonicwall Global VPN client and still had the issue.

Finally, removing Citrix DNE Lightweight Filter service from my network adapter solved the problem for me.

John

I'll second this, I connect to a couple of dozen different clients' servers using at least 10 different pieces of software; and I ripped out just about everything suggested here.  Only after uninstalling the Citrix DNE LightWeight Filter service from the network adaptor (and restarting) did the error go away.
I'm not putting back the other stuff (SonicWall client, Link-Layer Topology (Mapper I/O Driver and Responder) and QoS Packet Scheduler service) until this job is finished tomorrow, but I'll test as I add things back in and report back here.  

I did this.  Removed the old Global VPN client and re-added everything back in and it works fine.  I had 2 systems displaying this issue that both ran the old client.  I took just the client off the 2nd system and it corrected the issue.  I also removed the Citrix Client but I did not have to do a restart on either system.  Didn't see a need for that filter anyway and I am running perfectly normal without it.

I have had those Global VPN clients in place for quite some time even though I primarily utilize the SSL-VPN now.

This issue has plagued me for a long while on one system and it never occurred to me that the old client (since it was not being used) could cause this.  Thanks for the help John and Simon.

Simply running the Sonicwall client without actually connecting to any vpn actually resolved the issue for me.

THIS WORKED! I have no idea why. I just turned on the client, and then was able to connect to RDP sessions via my standard windows PPTP vpn. What horrible sorcery is behind this client!?

Thanks a ton for these simple and clear instructions that just work.  These days, with all the Microsoft bugs and crappy and failing software, it's nice to find friends and folks who simply find quick fixes that actually work.  So many times people make suggestions, but it's nice to find someone who bothered to take the time to help others solve theirs.  Thanks again Garth!

• Edited by Brandon Hawbaker Friday, March 14, 2014 4:05 PM

This also worked for me AMAZING -- I have tried just about everything in all other posts. In fact I was doing it and was able to use SSL VPN without knowing why. Today I tried it and this is definitely what results in me able to stably connect. I tried to connect to 5 different sonicwalls of different firmwares using 3 different versions of the NetExtender and only this solution of simply opening GVC worked for me. Thank you!!

Yup, this worked for me too.  Go figure.

Simply running the Sonicwall client without actually connecting to any vpn actually resolved the issue for me.

worked for me.

This worked for me!... Thanks!

Confirmed running the Sonicwall VPN Client while connecting works for me too.

And I'll add the I can connect to Win8.1 (from the same Win7 machine) without error without the VPN client running. Probably Microsoft added some way to encrypt RDP traffic that's not shared with Sonicwall's VPN client.

The Sonicwall Global VPN client started causing the error for me recently as well while trying to RDP into 2012r2 servers.  Removing the Sonicwall Global VPN client and rebooting did the trick. 

Ironically, I am RDP'ing into a 2012r2 server over a Sonicwall NetExtender client now successfully.

Yes, just simply running the Sonicwall Global VPN client (without connecting anything) allowed me to then connect to any RDP that uses a VPN. Uninstalling Sonicwall did not solve the problem. I had to reinstall and then run Sonicwall.

This worked for me as well. Thanks.

Hi,

Issue resolved by Local Area Connection -> Properties -> Configure -> Advanced -> IPv4 Large Send Offload =Disabled.

Thank you.